 |
MarchExternal release date is TBD.
| Caching enhanced |
|---|
|
| Issue/Summary: |
| Solution/Technical Notes: |
| Implementation Notes: This feature requires a Requirements and Content Editor Tool / Expere Engine / Content Style Sheets / Expere Server Tools (choose one: Expere Administration Tool/Customer Facing Outlines/Build Doc Previews/Data Dictionary Builder) update. |
| Fillable Fields now support XML special characters |
|---|
|
| Issue: Users reported an issue when sending a transaction data value containing a special character in a pre-populated fillable text field. As a result, the document would not assemble due to the special character. |
| Summary: Fillable fields now support all XML special characters and render properly as a PDF and the XML response file. |
| Implementation Notes: No user action is required. |
February - Expere Engine 17.1.0.4102External release date is TBD.
| <SaveInDatabase/> behavior modified |
|---|
|
| Summary: We have enhanced the <SaveInDatabase/> element behavior for Select API calls. |
| Technical Notes: We have changed the default value from "true" to "false" for the <SaveInDatabase/> element in Select API calls. With this change, Select requests by default are no longer saved in the database. |
| Implementation Notes: Users should change the <SaveInDatabase/> element value to "true" to save Select requests in the database. |
| eSequence fields behavior enhanced |
|---|
|
| Summary: We have enhanced the behavior of sequencing fillable fields and signature points, to ensure that sequencing is implemented when the PDF is being merged or if the XML contains duplicate Names. |
| Implementation Notes: A combination of the <WKES/> element <MergePDF/> element settings determine sequencing behavior. The Expere Developer Guide: Sequencing contains extensive details on this enhanced sequencing behavior. |
| Expere Engine: ability to merge closing disclosures with addendum |
|---|
|
Summary: We have implemented a new <MergeTRIDDocs/> element that allows users to merge the following TRID documents through the request file:
|
| Technical Notes: With this enhancement, if the <MergeTRIDDocs/> flag is set to "true" in the Expere request, the addendums above are merged with the associcated closing disclosure into a single standard PDF file. As a result, the closing disclosure, merged with the addendum, is returned in the response with the normal closing disclosure instance name and the addendum instance is removed from the response. |
| Implementation Notes: For more information, see MergeTRIDDocs flag - PDF in the Expere Developer Guide |
| Caching database organizations configurable |
|---|
|
| Summary: Previously, all organizations were cached together, including OPPSA organization. This presented an issue when multiple Expere instances were used, including the hosted OPPSA application. Expere cleared the AllOrganizationsList object from the database whenever OPPSA changed, but this was insufficient. |
Technical Notes: We have implemented an enhancement to our database caching capabilities: com.bankerssystems.database.organization.caching was added to the bsi.properties file.## When set to false the organization structure from the database, which includes the OPPSA organizations won't be cached. ## Set this to false if there will be more than one Expere server in an OPPSA environment ## The default is true if this key isn't found com.bankerssystems.database.organization.caching=true |
| Implementation Notes: By default the value is set to "true" but should be set to "false" when Expere installed with Document Generation Services. Users can modify the <ENABLE_ORGANIZATION_CACHE/> element within the transform.xml file. See Appendix: Sample Transforms.xml file for more information. |
| Expere Engine: Ability to produce merged disclosures for either PDF or PDF/A documents |
|---|
|
Summary: Previously in PBI 416188, we enhanced Expere to support the following documents in PDF/A format:
|
| Technical Notes: The request file contains a new <RequestUCD/> element that, when set to "True," produces the documents below in a PDF/A format, and if the addendum is produced, merges it with its respective closing disclosure. The merged document is returned in the response as the closing disclosure instance and the addendum instance is removed. If not setting the flag, documents are produced using the standard PDF format and the documents are not merged. |
| Implementation Notes: For more information, see RequestUCD flag - PDF/A in the Expere Developer Guide. |
| PDF Merge enhanced to include SignaturePointSet |
|---|
|
| Summary: We recently included support for PDF Merge functionality with Expere whereby a </SignaturePointSet> element is now returned in the response when at least one document has fields and PdfMerge is requested. |
| Implementation Notes: No user action is required. |
January - Expere Engine 2016.3.0.3995External release date is TBD.
| PDF/a now available in Expere |
|---|
|
Summary: Expere users can now produce the following documents in PDF/A format:
|
| Technical Notes: The request file now contains a new <RequestUCD/> element that, when set to "True," produces the documents above. If not setting the flag, documents are produced using the standard PDF format. |
| Implementation Notes: What is PDF/A format? It is an ISO 19005 compliance PDF file used for archiving and long-term preservation of electronic documents. For more information, see the following: |
| eSignature and Field Support checkbox selections enhanced to save in database |
|---|
|
| Issue: Previously, eSignature and Field Support settings from a transaction were not retained when resubmitting that same transaction. As a result, users were required to reenter these settings. |
Solution: The following eSignature and Field Support settings are saved in the database, regardless if "True," "False," or "NULL:"
|
| Implementation Notes: No user action is required. |
| BSI.properties file updated to include new eSignature PDF Merge flag in Expere installer |
|---|
|
Summary: We have updated the BSI.properties file for the Expere Wildfly installer to include the following lines:## Indicates whether the ESignatures and MergePDF output is enabled com.bankerssystems.expere.model.ESigPdfMerge=trueThis enables eSignature and PDF Merge functionality for Expere. |
| Implementation Notes: No user action is required. |
| Fillable field checkboxes behavior enhanced for all documents |
|---|
|
Summary: In a previous release, we implemented enhancements that return XY coordinates for all fillable fields (Expere Engine: continued enhancement of eSignatureAndFieldSupport and SignaturePointSet elements; Expere Engine: SignaturePointSet and eSignatureAndFieldSupport element changes). In this release, checkboxes associated with fillable fields now appear on all documents even if requesting X/Y coordinates. Note the following guidelines:
|
| Implementation Notes: For more information, see Using eSignature and Acroform fields. |
|